Sets the timeout duration for access control database on HNB-GW service instance to wait for dur minutes before purging the IMSI values received as White List from HMS/BAC.
After all HNBs de-registered, the Access Control database on HNB-GW maintain the IMSI White List received from HMS/BAC during HNB registration procedure in HNB-GW service for the configured dur in minutes before purging the list.
The dur is timeout value in minutes and must be an integer from 1 through 1440.
This command sets the timeout duration to maintain the IMSI White List received from HMS/BAC during HNB registration procedure in HNB-GW service for the configured dur in minutes after de-registration of all referenced HNBs from HNB-GW node and then purge the database.
associate gtpu-service svc_name
The svc_name must be an alphanumerical string from 1 through 63 characters.
Important: Another GTP-U service can be used to bind the HNB-GW service towards the Core Network and can be configured in HNB-PS Configuration mode. For more information on GTP-U service configuration, refer GTP-U Service Configuration Mode Commands.Following command associates GTP-U service named gtpu-hnb1 with specific HNB-GW service towards Home-NodeB side.
associate gtpu-service gtpu-hnb1
associate rtp pool pool_name
The pool_name must be an alphanumerical string from 1 through 31 characters.
Important: For IP pool (RTP pool) configuration, refer ip pool command in Context Configuration Mode Commands chapter.
Important: This command must be used to provide IP address for mapping of RTP streams on Iuh interface between HNB and HNB-GW.Following command associates RTP pool named rtp_1 with HNB-GW service for RTP stream end point from Home-NodeB:
associate rtp pool rtp_1
If hand-over is restricted the relocation request will be rejected with rejection cause “Relocation Not Supported In Target RNC Or Target System”.
If hand-over is restricted the Relocation Request message will be rejected with rejection cause “Relocation Not Supported In Target RNC Or Target System”.
Use of this keyword to make the configuration pass-through mode or not marking DSCP at all in the packets. Use of this keyword is allowed even when there is no previous DSCP parameter set.
Important: In this configuration no keyword is not meant to disable/remove a previous configuration, like other commands on ASR5000.sctp payload all dscp_code
udp payload { gtpu | rtcp| rtp} dscp_code
|
•
|
GTP-U: cs1
|
|
•
|
RTCP: ef
|
|
•
|
RTP: af41
|
following type of DSCP codes dscp_code are supported over IuH interface:
|
•
|
af11: Marks traffic as Assured Forwarding 11 PHB (high throughput data)
|
|
•
|
af12: Marks traffic as Assured Forwarding 12 PHB (high throughput data)
|
|
•
|
af13: Marks traffic as Assured Forwarding 13 PHB (high throughput data)
|
|
•
|
af21: Marks traffic as Assured Forwarding 21 PHB (low latency data)
|
|
•
|
af22: Marks traffic as Assured Forwarding 22 PHB (low latency data)
|
|
•
|
af23: Marks traffic as Assured Forwarding 23 PHB (low latency data)
|
|
•
|
af31: Marks traffic as Assured Forwarding 31 PHB (multimedia streaming)
|
|
•
|
af32: Marks traffic as Assured Forwarding 32 PHB (multimedia streaming)
|
|
•
|
af33: Marks traffic as Assured Forwarding 33 PHB (multimedia streaming)
|
|
•
|
af41: Marks traffic as Assured Forwarding 41 PHB (multimedia conferencing). This is the default DSCP code for RTP payloads in UDP protocol.
|
|
•
|
af42: Marks traffic as Assured Forwarding 42 PHB (multimedia conferencing)
|
|
•
|
af43: Marks traffic as Assured Forwarding 43 PHB (multimedia conferencing)
|
|
•
|
cs1: Marks traffic with Class Selector 1 (low priority data). This is the default DSCP code for GTP-U payloads in UDP protocol.
|
|
•
|
cs2: Marks traffic with Class Selector 2 (OAM)
|
|
•
|
cs3: Marks traffic with Class Selector 3 (broadcast video)
|
|
•
|
cs4: Marks traffic with Class Selector 4 (real-time interactive)
|
|
•
|
cs5: Marks traffic with Class Selector 5 (signaling). This is the default DSCP code for all SCTP payloads.
|
|
•
|
cs6: Marks traffic with Class Selector 6 (network control)
|
|
•
|
df : Marks traffic as Default Forwarding (best effort: DSCP = 0)
|
|
•
|
ef: Marks traffic as Expedited Forwarding PHB (telephony). This is the default DSCP code for RTCP payloads in UDP protocol.
|
This command adds DSCP marking on egress traffic going towards CN (CS/PS). To make the configuration pass-through mode or not marking DSCP at all in the packets, no variant of command is used. Use of no is allowed even when there is no previous DSCP configuration done.
Important: In this configuration no keyword is not meant to disable/remove a previous configuration, like with other commands on ASR5000.
Important: By default this command is Disabled.
Important: When DSCP configuration is not specified, system works in pass-through mode and DSCP value in the ingress (from CN) and egress (to HNB) data packets remain unchanged. Multiple traffic classes can share the same code point value.Use of this keyword to make the configuration pass-through mode or not marking DSCP at all in the packets. Use of this keyword is allowed even when there is no previous DSCP parameter set.
Important: In this configuration no keyword is not meant to disable/remove a previous configuration, like other commands on ASR5000.sctp payload all dscp_code
udp payload { gtpu | rtcp| rtp} dscp_code
|
•
|
GTP-U: cs1
|
|
•
|
RTCP: ef
|
|
•
|
RTP: af41
|
following type of DSCP codes dscp_code are supported over IuH interface:
|
•
|
af11: Marks traffic as Assured Forwarding 11 PHB (high throughput data)
|
|
•
|
af12: Marks traffic as Assured Forwarding 12 PHB (high throughput data)
|
|
•
|
af13: Marks traffic as Assured Forwarding 13 PHB (high throughput data)
|
|
•
|
af21: Marks traffic as Assured Forwarding 21 PHB (low latency data)
|
|
•
|
af22: Marks traffic as Assured Forwarding 22 PHB (low latency data)
|
|
•
|
af23: Marks traffic as Assured Forwarding 23 PHB (low latency data)
|
|
•
|
af31: Marks traffic as Assured Forwarding 31 PHB (multimedia streaming)
|
|
•
|
af32: Marks traffic as Assured Forwarding 32 PHB (multimedia streaming)
|
|
•
|
af33: Marks traffic as Assured Forwarding 33 PHB (multimedia streaming)
|
|
•
|
af41: Marks traffic as Assured Forwarding 41 PHB (multimedia conferencing). This is the default DSCP code for RTP payloads in UDP protocol.
|
|
•
|
af42: Marks traffic as Assured Forwarding 42 PHB (multimedia conferencing)
|
|
•
|
af43: Marks traffic as Assured Forwarding 43 PHB (multimedia conferencing)
|
|
•
|
cs1: Marks traffic with Class Selector 1 (low priority data). This is the default DSCP code for GTP-U payloads in UDP protocol.
|
|
•
|
cs2: Marks traffic with Class Selector 2 (OAM)
|
|
•
|
cs3: Marks traffic with Class Selector 3 (broadcast video)
|
|
•
|
cs4: Marks traffic with Class Selector 4 (real-time interactive)
|
|
•
|
cs5: Marks traffic with Class Selector 5 (signaling). This is the default DSCP code for all SCTP payloads.
|
|
•
|
cs6: Marks traffic with Class Selector 6 (network control)
|
|
•
|
df : Marks traffic as Default Forwarding (best effort: DSCP = 0)
|
|
•
|
ef: Marks traffic as Expedited Forwarding PHB (telephony). This is the default DSCP code for RTCP payloads in UDP protocol.
|
This command adds DSCP marking on egress traffic going towards HNB. To make the configuration pass-through mode or not marking DSCP at all in the packets, no variant of command is used. Use of no is allowed even when there is no previous DSCP configuration done.
Important: In this configuration no keyword is not meant to disable/remove a previous configuration, like with other commands on ASR5000.
Important: By default this command is Disabled.
Important: When DSCP configuration is not specified, system works in pass-through mode and DSCP value in the ingress (from CN) and egress (to HNB) control and data packets remain unchanged. Multiple traffic classes can share the same code point value.
Caution: Removing the PLMN identifier is a disruptive operation; the HNB-GW service shall be re-started.mcc mcc_num
mcc_num must be an integer value from 101 through 998.
mnc mnc_num
mcc_num must be an integer value from 01 through 99 or 100 through 998.
Caution: Changing or removing the PLMN identifier is a disruptive operation; the MME service shall be re-started.The following command configures the radio network PLMN identifier with MCC value as 102 and MNC value as 20 for an HNB-GW service:
ranap reset {ack-timeout timer_value | guard-timeout g_timer | hnbgw-initiated | max-retransmissions retries}
ack-timeout timer_value
timer_value must be an integer value from 5 through 10.
guard-timeout g_timer_value
g_timer_value must be an integer value from 5 through 10.
max-retransmission retries
retries must be an integer value from 0 through 2. When 0 is used retransmission is disabled.
interval dur
dur is measured in seconds and can be configured to any integer value from 5 to 30.
Important: The same interval is applicable for all kinds of RTCP packets/ reports across all sessions on an HNB-GW service.The following command configures the RTCP report generation interval to 15 seconds on an HNB-GW service for RTP stream:
default sctp {alpha-rto | beta-rto | checksum-type | cookie-life | max-retx [ init | path | assoc] | mtu-size [start | min | max ] | rto { initial | min | max} | sack-frequency | sack-period | max-in-strms | max-out-strms }
|
•
|
alpha-rto: 5 seconds
|
|
•
|
beta-rto: 10 seconds
|
|
•
|
checksum-type: CRC32
|
|
•
|
cookie-life: 600 ms
|
|
•
|
max-retx init: 5 retries
|
|
•
|
max-retx path: 5 retries
|
|
•
|
max-retx assoc: 10 retries
|
|
•
|
mtu-size min: 508 Bytes
|
|
•
|
mtu-size max: 1500 Bytes
|
|
•
|
mtu-size start: 508 Bytes
|
|
•
|
rto initial: 30 seconds
|
|
•
|
rto min: 10 seconds
|
|
•
|
rto max: 600 seconds
|
|
•
|
|
•
|
sack-period: 2 ms
|
|
•
|
max-in-strms: 4
|
|
•
|
alpha-rto alpha_rto_dur
dur is measured in seconds and can be configured to any integer value from 0 to 65535. A ‘zero’ value disables the timer in this configuration.
beta-rto beta_rto_dur
dur is measured in seconds and can be configured to any integer value from 0 to 65535. A ‘zero’ value disables the timer in this configuration.
adler32: specifies the SCTP association to use Adler32 checksum algorithm for packet validation. By default this is disabled.
crc32: specifies the SCTP association to use 32-bit cyclic redundancy check (CRC) algorithm for packet validation. By default this is enabled.
cookie-life cookie_life
cookie_life is measured in milliseconds and can be configured to any integer value from 500 to 120000.
max-retx [ init | path | assoc ] max_retry
init: This option sets the maximum attempts allowed after T1-init timer expires. If the T1-init timer expires then the HNB-GW retransmits INIT chunk and re-start the T1-init timer without changing state. This is repeated up to the configured times with this configuration. After that, the HNB-GW aborts the initialization process. Default number of attempts max_retry for this state is 5.
path: This option sets the maximum attempts allowed after T3-rtx timer expires. Each time the T3-rtx timer expires on any address, or when a HEARTBEAT sent to an idle address is not acknowledged within a RTO, the error counter of that destination address incremented. When the value in the error counter exceeds this protocol parameter of that HNB address, the HNB-GW marks the destination transport address as inactive. Default number of attempts max_retry for this state is 5.
assoc: This option sets the maximum number of consecutive retransmissions to its peer is allowed. If the value of this counter exceeds the limit configured with this keyword the HNB-GW considers the peer HNB unreachable and stop transmitting any more data to it. The SCTP association is automatically closed when the peer endpoint becomes unreachable. Default number of attempts max_retry for this state is 10.
max_retry can be configured to any integer value from 1 to 255.
mtu-size [ min | max | sart ] mtu_byte
min: This option sets the minimum size of MTU for SCTP association between HNB and HNB-GW. Default minimum MTU size mtu_byte is 508 Bytes.
max: This option sets the maximum size of MTU for SCTP association between HNB and HNB-GW. Default maximum MTU size mtu_byte is 1500 Bytes.
start: This option sets the size of MTU for SCTP association at the start of session between HNB and HNB-GW. Default MTU size mtu_byte at initial sate is 508 Bytes.
mtu_byte can be configured to any integer value from 508 to 65535.
initial ini_rto_dur: This option sets the initial retransmission timeout duration for SCTP association between HNB and HNB-GW. ini_rto_dur is RTO duration in seconds must be an integer between 1 through 1200. The default timeout value for ini_rto_dur is 30.
min min_rto_dur: This option sets the minimal retransmission timeout duration for SCTP association between HNB and HNB-GW. min_rto_dur is RTO duration in seconds must be an integer between 1 through 50. The default timeout value for min_rto_dur is 10.
max max_rto_dur: This option sets the maximum retransmission timeout duration for SCTP association between HNB and HNB-GW. max_rto_dur is RTO duration in seconds must be an integer between 5 through 1200. The default timeout value for max_rto_dur is 600.
sack-frequency sack_frq
sack_frq is the frequency after which SACK chunk is sent to HNB. sack_frq must be an integer value from 1 to 5.
sack-period sack_dur
sack_dur is the time period in seconds after which SACK chunk is sent to HNB and must be an integer value from 0 to 5. A ‘zero’ value disables the parameter.
max-in-strms in_strms
in_strms is the maximum incoming SCTP streams allowed from an associated HNB to HNB-GW and must be an integer value from 1 to 16.
max-out-strms out_strms
out_strms is the maximum outgoing SCTP streams allowed from an associated HNB to HNB-GW and must be an integer value from 1 to 16.
The following command sets the SCTP COOKIE life to 600 milliseconds on HNB-GW for the SCTP association:
address address
address must be an IP address in IPv4 or IPv6 notation.
port port_num
port_num must be an integer between 1 through 65535.
The following command sets the SCTP port number 999 on HNB-GW to listen from Home-NodeB over Iuh interface:
sctp bind port 999
The following command sets the SCTP address 1.2.3.4 of HNB-GW to use with Home-NodeB over Iuh interface:
sctp bind address 1.2.3.4
dur is measured in seconds and can be configured to any integer value from 5 to 30.
The following command sets the SCTP connection timeout duration to 15 second on HNB-GW after expiry of which the SCTP association is removed:
dur is measured in seconds and can be configured to any integer value from 1 to 300.
The following command sets the SCTP HEARTBEAT timeout duration to 15 second on HNB-GW after expiry of which the HNB-GW retransmits the HEARTBAT chunk to HNB over SCTP association:
security-gateway aaa authentication { first-phase | second-phase } context ctx_name aaa-group aaa_grp
first-phase specifies the parameters to be used for first phase of authentication while using SeGW functionality in an HNB-GW service. This associates the AAA parameters through AAA server group association with in it.
second-phase specifies the parameters to be used for second phase of authentication while using SeGW functionality in an HNB-GW service. This associates the AAA parameters through AAA server group association with in it.
context ctx_name aaa-group aaa_grp specifies the name of the pre-configured AAA server group and its context to associate AAA parameters to be used for first/second or both phase of authentication while using SeGW functionality in an HNB-GW service.
ctx_name specifies the name of the context in which AAA server group is configured.
aaa_grp specifies the name of the AAA server group configured in Context configuration mode with AAA parameters which need to be used for first/second or both phase of authentication while using SeGW functionality in an HNB-GW service.
Important: For more information on AAA server groups, refer AAA Server Group Configuration Mode Commands.
Caution: This is a critical configuration and need to be configured carefully when Security Gateway (SeGW) functionality required on HNB-GW service.The following command associates an AAA server group named sec_gw_grp1 with HNB-GW service to use specific AAA authentication parameters in first phase of authentication and another AAA server group named sec_gw_grp2 to use different AAA authentication parameter in second phase of authentication. Both AAA server groups are configured in same context named SeGW_ctx1:
security-gateway aaa authentication first-phase context SeGW1 aaa-group sec_gw_grp1security-gateway aaa authentication second-phase context SeGW1 aaa-group sec_gw_grp2
bind address address
address specifies the IPSec IP address in IPv4/IPv6 notation to be used for binding the IKEv2 IPSec tunnel (local bind address) to communicate with the Home-NodeBs using Iuh interface.
crypto-template cryp_name
cryp_name specifies the name of the pre-configured Crypto-map template which is configured in Crypto-Map Template Configuration Mode and associated with HNB-GW service to create IPSec tunnel with Home-NodeB during HNB-GW discovery procedure on Iuh interface.
context ctx_name
Caution: This is a critical configuration. The HNB-GW service can not be started without this configuration. Any change to this configuration would lead to restarting the HNB-GW service and removing or disabling this configuration stops the HNB-GW service.The following command binds the logical IP interface with the address of 1.2.3.4 to the HNB-GW service using existing IPsec Crypto-Map template crypto1 to establish IPSec tunnel with Home-NodeB:
The following command sets the system to strip the MAC address from user name received from user MS:
This command configures the NAS Node Selection Function (NNSF) timer (T-NNSF) which is used by the HNB-GW to store the IMSI and the relevant Global-CN-ID in the short term after Paging. This timer is used for Iu-Flex feature support.
tnnsf-timer dur
tnnsf-timer dur
Configures the timer value for NNSF timer (T-NNSF) in seconds, which is used by the HNB-GW to store the IMSI and the relevant Global-CN-ID in the short term after Paging.
dur must be an integer between 10 through 60.
Whenever the MSC sends the paging request with IMSI, the HNB-GW stores the Global_CN_ID of the node which issued the paging request message for the given IMSI and HNB-GW starts the tnnsf-timer. HNBGW stores the mapping of IMSI to Global_CN_ID until the tnnsf-timer expires
The following command sets the NNSF timer value to 30 seconds in an HNB-GW service instance:
dur is measured in seconds and can be configured to any integer value from 60 to 300.
The following command sets the UE registration timeout duration to 150 second on HNB-GW after expiry of which the UE is de-registered:
